-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ auth: use synthetic user/group when service account is not defined #1816
base: main
Are you sure you want to change the base?
✨ auth: use synthetic user/group when service account is not defined #1816
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
dfc5ccb
to
fbcc4a5
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1816 +/- ##
==========================================
+ Coverage 68.43% 68.48% +0.05%
==========================================
Files 63 64 +1
Lines 5132 5166 +34
==========================================
+ Hits 3512 3538 +26
- Misses 1390 1397 +7
- Partials 230 231 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
11210fc
to
e44c4d2
Compare
I'd like to have a discussion on the |
1c2f38f
to
73e6080
Compare
I put next to no critical thought into the name and group names. @thetechnick you propose the following?
|
Signed-off-by: Joe Lanford <[email protected]>
Signed-off-by: Per Goncalves da Silva <[email protected]>
Signed-off-by: Per Goncalves da Silva <[email protected]>
Signed-off-by: Per Goncalves da Silva <[email protected]>
Signed-off-by: Per Goncalves da Silva <[email protected]>
73e6080
to
fb13084
Compare
Signed-off-by: Per Goncalves da Silva <[email protected]>
Description
Today at a meeting among maintainers of OLMv1, we discussed an idea that @thetechnick proposed awhile back. That is: stop using service accounts and service account tokens. Instead use synthetic names with impersonation.
While we are now 1.0.0 with support for service accounts, we can deprecate that feature and recommend attaching permissions to synthetic users/groups instead.
This PR demonstrates how we might do this. But with the API change, we should write up a detailed design and gain consensus.
This PR uses:
"olmv1:clusterextensions:<clusterExtensionName>:admin"
["system:authenticated", "olmv1:clusterextensions:admin"]
But I'm not sure this is the best setup. There's more discussion to be had around what sythentic names/groups we could derive from a cluster extension.
Reviewer Checklist